-
-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardise repo per module template as of April 2023 #254
Conversation
// after the provider has processed the request, to ensure that the | ||
// provider recognizes the id. | ||
setImmediate(() => | ||
setTimeout(() => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setImmediate
is not available in recent versions of Node.js and/or browsers, so I've swapped this out to use setTimeout
. For our purposes, it does effectively the same.
@@ -298,6 +308,7 @@ export class MetaMaskInpageProvider extends AbstractStreamProvider { | |||
*/ | |||
send<T>(payload: SendSyncJsonRpcRequest): JsonRpcResponse<T>; | |||
|
|||
// eslint-disable-next-line @typescript-eslint/promise-function-async |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
send
can return a Promise
, so ESLint wants to add async
to it. This changes the behaviour of the function, however, as anything would make it return a Promise
. To avoid this we have to suppress this rule here.
Please document the breaking changes in this PR in the description. |
8048d34
to
ba7f3a5
Compare
This updates the repo to the latest standards. This includes a bump to the ESLint configurations, meaning I had to fix a bunch of ESLint-related errors.
Breaking changes